---
title: "Side Trips"
space: "Fleet ms"
url: "https://support.aakvatech.com/Fleet MS/side-trips"
updated: "2026-07-22"
---

 
## 1. Overview
The **Side Trips** child table is part of the Trip management system in the *VSD Fleet MS* module. It is used to log any unplanned or auxiliary trips made during the main trip journey—such as diversions for maintenance, fuel stops, or deliveries outside the main route.

---

## 2. Key Features
- Records both the **starting** and **ending** locations of a side trip.
- Captures date range with **Start Date** and **End Date**.
- Stores **reason** for the diversion (mandatory field).
- Tracks total **distance**, **expense**, and **fuel** used for each side trip.
- Editable inline via the Trip doctype for convenience.

---

## 3. Pre-Requisites
Before using the Side Trips table:
- A parent **Trip** document should exist.
- Users should understand trip structure and common reasons for side trips (e.g., detours, service stops).
- Proper role permissions to edit or create entries must be assigned.

---

## 4. Step-by-Step Usage
1. Open the relevant **Trip** document.
2. Navigate to the **Side Trips** section (child table).
3. Click **Add Row** to insert a new side trip.
4. Fill in the following:
   - **Starting Location** and **Start Date**
   - **Ending Location** and **End Date**
   - **Reason** for the side trip
   - **Total Distance**, **Total Expense**, and **Total Fuel**
5. Save the Trip document to store the side trip details.

---

## 5. Script Customizations
Currently, there are no backend validations or automation scripts in the `SideTrips` class (`pass`). However, potential enhancements could include:
- Auto-calculation of distance or fuel based on known coordinates.
- Validation to ensure date logic (e.g., End Date >= Start Date).
- Expense/fuel syncing with Expense Claims or Fuel Logs.

---

## 6. Troubleshooting (Common Errors and Resolutions)

| Issue                         | Cause                                | Resolution                                               |
|------------------------------|--------------------------------------|----------------------------------------------------------|
| Cannot save entry            | Missing required fields              | Ensure all mandatory fields (locations, reason, totals) are filled. |
| Invalid date range           | Start Date is after End Date         | Correct the dates so Start Date ≤ End Date.              |
| Distance or fuel is zero     | Data entry error or omission         | Verify and input realistic values for distance/fuel.     |

---

## 7. User Roles and Permissions

| Role           | Permission                     |
|----------------|--------------------------------|
| Fleet Manager  | Full access (Read, Write)      |
| Trip Officer   | Can add and update side trips  |
| Driver         | Usually no access (unless customized) |

> 🔐 Permissions are inherited from the parent **Trip** doctype.

---

## 8. Key Notes
- Every side trip is recorded with clear operational data: **reason**, **duration**, and **cost**.
- Ensure accurate distance and fuel logging for analysis and reporting.
- If total expense involves multiple currencies or costs, standardize the value format for consistency.

---

## 9. What Business Process Pain Point Does It Help Remove
The **Side Trips** child table improves **operational transparency** by tracking off-route activities. It mitigates issues like:
- Unauthorized diversions
- Poor fuel and cost accountability
- Data loss during manual trip logging

This functionality ensures **every deviation** is well-documented, contributing to better decision-making, performance evaluation, and compliance auditing in fleet operations.